From b67b0390b9b6dbaed53a6a3a849b32f3c757eaa9 Mon Sep 17 00:00:00 2001 From: Gerd Moellmann Date: Mon, 4 Dec 2000 14:48:10 +0000 Subject: [PATCH] (Fread_key_sequence): Don't start the busy cursor timer after having read a key. It's not good for code reading several keys in a loop, like an input method. --- src/keyboard.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/keyboard.c b/src/keyboard.c index 07f0bc3c423..b23e08959e4 100644 --- a/src/keyboard.c +++ b/src/keyboard.c @@ -8858,9 +8858,13 @@ DEFUN ("read-key-sequence", Fread_key_sequence, Sread_key_sequence, 1, 5, 0, prompt, ! NILP (dont_downcase_last), ! NILP (can_return_switch_frame), 0); +#if 0 /* The following is fine for code reading a key sequence and + then proceeding with a lenghty compuation, but it's not good + for code reading keys in a loop, like an input method. */ #ifdef HAVE_X_WINDOWS if (display_busy_cursor_p) start_busy_cursor (); +#endif #endif if (i == -1) -- 2.30.2